home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Visual Basic Source Code
/
Visual Basic Source Code.iso
/
vbsource
/
proa32
/
knownbug.txt
< prev
next >
Wrap
Text File
|
1997-09-14
|
4KB
|
101 lines
Known bugs and limitations in Project Analyzer 4.0
Please report any new bugs to vbshop@aivosto.com.
===========
Limitations
===========
- The size of variable, constant and procedure names is restricted to 64
characters to save some memory. Longer names are truncated.
==================
Known misbehaviour
==================
- Long lines don't word wrap on some report types
- Long procedural call tree reports (All procedures) can hang the computer
- MyClass.MyProperty = 987 works OK (MyProperty Let), but
MyClass(123).MyProperty = 987 doesn't (thinks it's MyProperty Get)
Problem with subscript.
- In the hypertext window, letters in DefType statements may be
mistaken for one-letter variable names
- In the hypertext window, if you have two different definitions with the
same name (e.g. Form1.MyVar and Form2.MyVar), the program may
highlight the both in red when only the other one should be highlighted
===============================
Deficiencies in VB 3.0 features
===============================
- The Summary report shows somewhat distorted figures for
1. Global Name Table: Type definitions and DLLs declarations are
not calculated correctly.
2. Global Symbol Table: type definitions are excluded, and everything
else is assumed to take 10 bytes of memory.
Use freeware VB Space (by Gregg Irwin) for more exact calculations
- Can't analyze files saved as binary. Save as text instead.
===============================
Unsupported VB 4.0/5.0 features
===============================
- Compiler directives (#if xyz then)
- Line continuation character "_"
- Late-bound references. Example:
Forms(2).DoSomething
Project Analyzer can't know which form the call goes to, because
Forms(2) may be of any of your forms. This applies to all object
references that are of a general type (e.g. As Form, As Object)
and not a specific type (As MyForm, As MyObject).
===========================
Unsupported VB 5.0 features
===========================
- Controls on UserForms (.dsr/.dsx files)
- Project Group Files (.vbg)
- Inherits statement (polymorphism) supported partially. A procedure that
implements an interface procedure is dead only if the procedure it
implements is also dead. That's because polymorphed calls are bound
finally at run-time.
- If a class is supposed to be used outside the project, its members
may be "dead". This is a problem e.g. with ActiveX EXE/DLL projects.
========================
Deficiencies in FRX view
========================
- Supports the most usual data types and controls, like PictureBox.Picture,
ListBox.List, ListBox.ItemData, TextBox.Text, MouseIcon etc.
- Some properties that are not supported (others exist):
AniButton.Picture, SSCommand.Picture
======================
Help Compiler Warnings
======================
You can ignore the following warning in HCW.EXE:
HC2002: Note:
The keywords "xyz" and "Xyz" are identical except for case.
Help Workshop has modified one keyword to match the other.
================
For best results
================
- Always declare your local variables (use Option Explicit)
- Always save your files as text (VB 3.0)
- Use MS Word as RTF editor
- Wait for the analysis to end completely (it has 2 phases)
- VB 5.0: Project Analyzer is at its best analyzing Standard EXE
projects. You can of course analyze ActiveX projects too, but
public classes, for example, may have "dead" members that aren't
dead in reality (because they are used outside the project)